Moving back into RfC phase since 10e5220 adds a new .status.upgradingProductVersion CRD field.

Moving back into RfC phase since 10e5220 adds a new .status.upgradingProductVersion CRD field.

I didn't see the new field in the CRD YAML.

My bad, forgot to make crds. a9809ba

We could probably move it back to voting to speed it up.
I'll withhold my PR Approval until it's back out of RfC.

TLDR

pub struct HdfsClusterStatus {
    /// The product version that the HDFS cluster is currently running.
    ///
    /// During upgrades, this field contains the *old* version.
    pub deployed_product_version: Option<String>,

    /// The product version that is currently being upgraded to, otherwise null.
    pub upgrading_product_version: Option<String>,
}

Which works for me. WDYT of using upgrade_target_product_version to make it a bit more clear? Or would you consider this too chatty?

Sounds like an improvement to me.

0604aa6

Moving back into voting. Please vote on this comment.

Voting finished, accepted

Current merge blockers are:

• Rolling HDFS upgrade #571 (comment) requires approval from @NickLarsenNZ
• We need a new operator-rs release with Add iter::reverse_if helper operator-rs#838